Responsive Dashboard Layouts and Device Previews in Tableau – Complete Detailed Notes
Course: Tableau Training
Topic: Responsive Dashboard Layouts and Device Previews
Learning Objective: Understand how to design Tableau dashboards for desktop computers, tablets, and mobile phones; configure dashboard sizing; create device-specific layouts; use Device Preview; and test dashboard usability across different screen sizes.
Course Link: Explore Tableau Training
Demo Link: Register for a Tableau Course Demo
1. Introduction to Responsive Dashboard Layouts
A responsive dashboard layout is a dashboard design that adapts to the available viewing space and provides a usable experience across different screen sizes. In Tableau, responsive dashboard design involves choosing suitable dashboard dimensions, organizing objects with layout containers, configuring device-specific layouts, and testing the dashboard on different devices.
Business users may access the same dashboard from a desktop computer in the office, a tablet during a meeting, or a mobile phone while travelling. A dashboard designed only for a large monitor may become difficult to use on a smaller screen because charts, filters, labels, and legends can become crowded.
Tableau supports device-specific layouts for desktop, tablet, and phone viewing. These layouts can provide different arrangements of the same dashboard content for different screen sizes. Read Tableau's official guide to creating dashboard layouts for different device types.
Example
Consider a sales dashboard containing the following components:
- Total Sales KPI.
- Total Profit KPI.
- Monthly Sales Trend.
- Sales by Region chart.
- Region and Order Date filters.
- Product Category filter.
On a desktop, the KPI cards can appear in one row, with two charts underneath. On a phone, the KPI cards may be stacked vertically, and the charts may appear one after another to support vertical scrolling.
2. What Is a Responsive Dashboard?
A responsive dashboard is designed to remain readable and usable when the available viewing area changes. The goal is not necessarily to make every object look identical on every device. Instead, the goal is to preserve important information and make interactions comfortable for the user.
Main Characteristics
- Flexible layout: Dashboard objects fit the available space as intended.
- Readable content: Titles, labels, values, and legends remain easy to understand.
- Usable filters: Users can access filter controls without excessive scrolling or accidental selections.
- Appropriate visualization sizes: Charts are large enough to communicate their information.
- Device-specific arrangements: The layout can be customized for different device types.
- Consistent user experience: Users can understand the dashboard regardless of the device they use.
3. Why Are Responsive Dashboard Layouts Important?
Responsive dashboard layouts help organizations make their data accessible to users who work in different locations and use different devices.
Key Benefits
- Improved accessibility: Users can view important metrics on phones, tablets, and desktops.
- Better readability: The dashboard can be arranged to suit the available display area.
- Improved navigation: Filters, charts, and controls can be positioned where users can easily find them.
- Reduced clutter: Less important objects can be removed from a compact device layout when appropriate.
- Better decision-making: Important KPIs and trends remain accessible to business users.
- Greater flexibility: One published dashboard can provide suitable layouts for multiple device types.
- Better presentation: A dashboard can be prepared for office monitors, meeting-room displays, and mobile access.
4. Understanding Dashboard Size in Tableau
Dashboard size determines the overall dimensions of the dashboard. It influences how charts, filters, legends, and other objects fit within the available space.
Before designing a responsive dashboard, identify the primary viewing environment and select an appropriate sizing strategy.
Dashboard Sizing Options
| Option |
Description |
Best Use |
| Fixed Size |
Uses specified dashboard dimensions. |
Dashboards designed for a known screen or presentation size. |
| Automatic |
Allows the dashboard dimensions to adapt to the available viewing area. |
Simple dashboards that can tolerate resizing. |
| Range |
Allows minimum and maximum dimensions to be specified. |
Dashboards that need flexibility within controlled size limits. |
4.1 Fixed Size
With a fixed-size dashboard, you specify the intended width and height. This approach gives you more predictable control over object placement, but the dashboard may not fit every viewing area equally well.
Example: A sales dashboard designed for a large office monitor can use a fixed desktop size. However, its layout should still be tested if users will access it through smaller browser windows.
4.2 Automatic Size
Automatic sizing allows Tableau to adapt the overall dashboard dimensions to the available display area. It may be useful for simple dashboards, but it does not guarantee that every visualization will remain readable or well proportioned.
Complex dashboards with many charts may become cramped or require scrolling when automatically resized. Always test the result instead of assuming that automatic sizing alone makes a dashboard responsive.
4.3 Range Size
Range sizing lets you define minimum and maximum dashboard dimensions. This can help prevent a dashboard from becoming too small or too large while allowing some flexibility.
Example: A dashboard may be designed to operate within a range of supported desktop browser sizes. The appropriate limits depend on the dashboard content and the needs of its users.
How to Configure Dashboard Size
- Open your Tableau workbook.
- Select the dashboard you want to configure.
- Open the Dashboard pane.
- Locate the Size setting.
- Choose Fixed Size, Automatic, or Range, depending on your requirements and available options.
- If you choose Fixed Size, configure the intended width and height.
- If you choose Range, configure suitable minimum and maximum dimensions.
- Review the dashboard and check whether objects remain readable and properly arranged.
Official reference: Tableau visual best practices and dashboard sizing.
5. Understanding Device-Specific Dashboard Layouts
Device-specific layouts allow you to arrange dashboard objects differently for desktop, tablet, and phone displays. They are particularly helpful when one dashboard must support both large screens and compact mobile screens.
In Tableau, the Default dashboard acts as the main dashboard layout. Device layouts can then provide customized arrangements for supported device types.
Common Device Layouts
| Device Type |
Typical Characteristics |
Recommended Design Approach |
| Desktop |
Wide display area and more room for simultaneous charts. |
Use multiple columns, KPI rows, and side-by-side charts where appropriate. |
| Tablet |
Moderate display area, with portrait and landscape orientations. |
Reduce unnecessary columns and arrange related content into compact sections. |
| Phone |
Limited width and commonly used in portrait orientation. |
Prioritize important KPIs, use a vertical layout, shorten titles, and simplify controls. |
Default Layout and Device Layouts
- Default layout: The main dashboard layout containing the views and objects used as the basis for device-specific arrangements.
- Desktop layout: A layout that can be customized for desktop viewing.
- Tablet layout: A layout that can be customized for tablet viewing.
- Phone layout: A layout that can be automatically generated or customized for phone viewing.
Important: Desktop and tablet layouts are independent once created. Phone layouts can be configured to reflect changes to the Default dashboard automatically or edited independently. When editing a device layout, review it again after changing the underlying worksheets or dashboard content.
6. What Is Device Preview in Tableau?
Device Preview is a Tableau dashboard authoring feature that allows you to inspect how a dashboard appears on different device types and screen configurations. It helps identify layout issues before the dashboard is published.
Using Device Preview, you can select a device type, choose supported device models, rotate the preview between portrait and landscape, and add device-specific layouts where supported.
Benefits of Device Preview
- Checks whether charts fit within a device's display area.
- Helps identify clipped titles and labels.
- Reveals filters and legends that take up too much space.
- Helps determine whether a phone layout should be rearranged.
- Allows comparison of portrait and landscape orientations.
- Supports a more consistent user experience before publishing.
7. How to Use Device Preview
Follow these steps to preview your dashboard across different device types.
- Open your workbook in Tableau Desktop or a supported authoring environment.
- Open the dashboard you want to inspect.
- In the Dashboard pane, click Device Preview.
- Use the device-type selector to choose Desktop, Tablet, or Phone, where available.
- Choose a supported device model or screen configuration.
- Use the rotate control to inspect portrait and landscape orientations.
- Inspect the dashboard for clipped content, crowded filters, excessive scrolling, or unreadable labels.
- If needed, select Add Layout for the device type you want to customize.
- Make the necessary layout changes.
- Repeat the preview process for the other device types.
Official reference: Create Dashboard Layouts for Different Device Types.
8. Adding Device-Specific Layouts
When the default arrangement does not work well on a particular screen, you can add a device-specific layout and customize the objects it contains.
Steps to Add a Device Layout
- Open the dashboard.
- Click Device Preview in the Dashboard pane.
- Select the desired device type, such as Tablet or Phone.
- Click Add Layout for the selected device type.
- Choose the custom layout option where available.
- Arrange the dashboard objects to suit the selected screen size.
- Adjust the sizing behavior and spacing.
- Preview the result using different supported device models.
- Repeat the process for other device types as required.
Why Create Separate Layouts?
A separate layout lets you make design choices that are appropriate for each screen instead of forcing every device to use the same arrangement.
For example, a desktop layout may show a line chart and a regional bar chart side by side. The phone layout may stack the same charts vertically so that each chart has enough width to display its labels.
9. Understanding Device Layout Sizing Options
After adding a device layout, review its sizing options. The available options may vary by device type and Tableau version.
| Option |
How It Works |
When to Use It |
| Default |
Uses the size behavior associated with the default dashboard. |
When the default sizing works for the device layout. |
| Fit All |
Resizes the dashboard content to fit within the device frame. |
When fitting all objects into the visible area is important. |
| Fit Width |
Fits content to the width of the device frame while allowing the layout's height to remain fixed. |
Often useful for phone layouts that support vertical scrolling. |
9.1 Fit All
Fit All attempts to make all dashboard items fit within the available device frame. This can reduce the need for scrolling, but it may also shrink charts, labels, and other objects.
Example: A dashboard with several charts may fit inside a tablet preview, but the text could become too small to read. If this happens, simplify or rearrange the layout rather than relying only on automatic resizing.
9.2 Fit Width
Fit Width adapts the dashboard content to the device frame's width while maintaining a fixed height for the layout. This can work well for phone dashboards designed for vertical scrolling.
Example: A mobile sales dashboard can display KPI cards first, followed by a monthly sales chart and a regional chart farther down the page.
9.3 Choosing the Right Option
- Use Fit All when the dashboard contains a small number of objects that remain readable when scaled.
- Consider Fit Width for phone layouts with vertically stacked content.
- Use Default when the existing dashboard size behavior is appropriate.
- Always inspect the result in Device Preview before publishing.
10. Designing a Desktop Dashboard Layout
Desktop screens offer more horizontal space, allowing several visualizations to be displayed simultaneously. The layout should still be organized so that the most important information is easy to identify.
Recommended Desktop Layout
- Place the dashboard title at the top.
- Arrange important KPI cards in a horizontal row.
- Place related charts side by side when their labels remain readable.
- Group filters in a consistent location.
- Keep legends close to the charts they explain.
- Use consistent padding and alignment.
Desktop Example
---------------------------------------------------------
| SALES DASHBOARD |
---------------------------------------------------------
| TOTAL SALES | TOTAL PROFIT | ORDERS | AVG. ORDER VALUE |
---------------------------------------------------------
| MONTHLY SALES TREND |
---------------------------------------------------------
| SALES BY REGION | SALES BY CATEGORY |
---------------------------------------------------------
| DATE FILTER | REGION FILTER |
---------------------------------------------------------
This is a conceptual layout. The final placement of filters depends on the dashboard's purpose and the available screen size.
11. Designing a Tablet Dashboard Layout
Tablets have less display space than most desktop monitors. Their layouts should balance the need to display multiple metrics with the need to keep charts and filters usable.
Recommended Tablet Design
- Use fewer columns than the desktop layout when necessary.
- Keep the most important KPI cards near the top.
- Stack charts vertically if side-by-side placement makes labels too small.
- Use concise chart titles and labels.
- Group filters to avoid scattering controls across the screen.
- Check both portrait and landscape orientations.
Tablet Example
--------------------------------------
| SALES DASHBOARD |
--------------------------------------
| TOTAL SALES | TOTAL PROFIT |
--------------------------------------
| SALES TREND |
--------------------------------------
| SALES BY REGION |
--------------------------------------
| FILTERS |
--------------------------------------
Use the tablet preview to decide whether a two-column arrangement is still readable or whether a single-column layout works better.
12. Designing a Mobile Phone Dashboard Layout
Mobile dashboards require careful prioritization because the display area is limited. A phone dashboard should focus on the most useful metrics and provide a straightforward way to access supporting details.
Recommended Mobile Design Principles
- Prioritize key metrics: Show the most important KPIs first.
- Use a vertical layout: Stack charts to make better use of the available width.
- Shorten titles: Avoid long titles that wrap across several lines.
- Simplify filters: Keep only the most useful controls in prominent positions.
- Reduce unnecessary white space: Use space efficiently without making controls difficult to tap.
- Keep labels readable: Avoid shrinking text excessively to fit more content.
- Limit complexity: Remove or reposition secondary charts if they do not support the main mobile task.
- Support scrolling: Arrange content in a logical sequence when the dashboard is taller than the screen.
Mobile Example
----------------------------
| SALES SUMMARY |
----------------------------
| TOTAL SALES |
| ₹12,50,000 |
----------------------------
| TOTAL PROFIT |
| ₹2,10,000 |
----------------------------
| MONTHLY SALES TREND |
| |
----------------------------
| SALES BY REGION |
| |
----------------------------
| FILTERS |
----------------------------
The example demonstrates a vertical structure. The actual dashboard should use the available device layout and sizing controls to achieve a readable result.
13. Understanding Auto-Generated and Custom Phone Layouts
Tableau can automatically generate a phone layout based on the Default dashboard. This is useful as a starting point, but the generated layout may not perfectly match the intended mobile experience.
Auto-Generated Phone Layout
- Uses an automatically arranged phone-friendly version of dashboard content.
- Can reflect changes to the Default dashboard when configured to stay linked.
- Can save time during initial mobile dashboard development.
- Should still be inspected for content order, readability, and usability.
Custom Phone Layout
- Allows the author to arrange items specifically for mobile users.
- Can remove objects from the phone layout without deleting them from the Default dashboard.
- Provides greater control over content priority and layout order.
- Requires additional maintenance when the Default dashboard changes.
How to Customize a Phone Layout
- Open Device Preview and select Phone.
- Choose the option to edit or customize the phone layout.
- Inspect the list of available dashboard items.
- Arrange the most important content near the top.
- Remove unnecessary objects from the phone layout when appropriate.
- Adjust spacing, sizing, and the order of charts.
- Preview the result on supported phone models.
Important: Removing an item from a device-specific layout does not necessarily delete it from the Default dashboard. Check the layout's edit mode before making changes.
14. Optimizing Phone Layouts
Tableau provides options to optimize manually customized phone layouts. These options can help improve the arrangement of items and reduce unnecessary space.
Phone Optimization Checklist
- Place key metrics first.
- Remove redundant chart titles or labels where they are not needed.
- Keep filter controls easy to locate.
- Reduce excessive gaps between objects.
- Use padding or Blank objects when intentional spacing is required.
- Ensure charts have enough width to communicate their information.
- Keep important controls accessible without requiring excessive scrolling.
In Tableau, use the phone layout menu and the available Optimize Layout option when supported. Remember that optimizing the current layout does not necessarily mean that it will continue to mirror all future changes to the Default dashboard.
15. Testing Portrait and Landscape Orientations
Mobile phones and tablets can be used in portrait or landscape orientation. A layout that works in one orientation may not work equally well in the other.
| Orientation |
Advantages |
Design Considerations |
| Portrait |
Supports vertically stacked content and convenient scrolling on phones. |
Keep charts narrow enough to fit but wide enough for labels. |
| Landscape |
Provides more horizontal space for maps, timelines, and side-by-side charts. |
Check the reduced vertical space and ensure important content remains visible. |
Testing Steps
- Open Device Preview.
- Select Phone or Tablet.
- Preview the dashboard in portrait orientation.
- Check titles, charts, labels, filters, and legends.
- Rotate the preview to landscape.
- Check whether any content becomes clipped or difficult to use.
- Adjust the device layout if necessary.
16. Responsive Layouts and Dashboard Interactivity
Filters, parameters, legends, and dashboard actions may behave differently from a usability perspective when the screen becomes smaller. A mobile dashboard should make its interactive controls easy to understand and use.
Best Practices for Filters
- Prioritize the filters users need most often.
- Use concise names and clear labels.
- Group related filters in a dedicated section.
- Avoid placing too many filter controls above the main visualization.
- Test whether the controls are easy to access in portrait orientation.
Best Practices for Dashboard Actions
- Make clickable or selectable elements easy to identify.
- Use clear titles and instructions where interactions may not be obvious.
- Test filter actions and highlight actions on the published dashboard.
- Check that interactions do not require excessive precision on a small screen.
- Verify that tooltips and supporting details remain useful on mobile devices.
17. Responsive Dashboard Design and Performance
A dashboard can have a well-designed layout but still provide a poor mobile experience if it loads slowly. Mobile users may have limited bandwidth or may need information quickly.
Performance Best Practices
- Remove worksheets and dashboard objects that do not contribute useful information.
- Avoid adding unnecessary filters and complicated interactions.
- Use appropriate data sources and extracts where suitable.
- Limit the number of marks displayed when possible.
- Reduce unnecessary dashboard complexity.
- Test load time and interaction speed after publishing.
- Prioritize a small number of meaningful visualizations on phone layouts.
Key point: Responsive design includes both visual usability and performance. A dashboard that fits a screen but loads slowly still provides a poor user experience.
18. Publishing and Testing Device-Specific Layouts
After configuring the layouts, publish the workbook to Tableau Server or Tableau Cloud, depending on your environment. Device-specific layouts are used when viewers access the published dashboard through supported viewing experiences.
Publishing Checklist
- Save the workbook.
- Verify that the Default dashboard is complete.
- Check the desktop, tablet, and phone layouts you created.
- Review the layout-specific sizing and content.
- Publish the workbook to the appropriate Tableau Server or Tableau Cloud site.
- Open the published dashboard in a browser or supported mobile application.
- Test the dashboard at different browser window sizes.
- Check that the intended device layout is selected.
- Test filters, actions, tooltips, and other interactive features.
Tableau selects a device layout based on the available viewing area, including the dimensions of the embedded view when a dashboard is embedded. Therefore, a device layout may be selected because of the browser or embedded container size, not only because of the physical device's name or screen resolution.
Official reference: Create and test dashboard layouts for different device types.
19. Common Responsive Dashboard Problems and Solutions
| Problem |
Possible Cause |
Solution |
| Dashboard content is clipped |
Objects do not fit the available dimensions. |
Review dashboard size, object dimensions, and device layout settings. |
| Text becomes too small |
Too many objects are being scaled into a small area. |
Simplify the layout or use a custom device layout. |
| Filters take up too much space |
Too many controls are visible at once. |
Prioritize the most important filters and rearrange them. |
| Phone layout is difficult to navigate |
Desktop content has not been adapted to mobile viewing. |
Use a vertical layout and prioritize important content. |
| Charts are too narrow |
Too many visualizations are placed side by side. |
Stack charts vertically in the tablet or phone layout. |
| Dashboard requires excessive scrolling |
Too many objects are included or spacing is inefficient. |
Remove unnecessary items and optimize layout spacing. |
| Desktop layout looks crowded |
Charts, filters, and legends compete for space. |
Group related content and reorganize the dashboard structure. |
| Phone layout does not reflect a recent change |
The phone layout may be customized independently. |
Review the phone layout and update it manually or adjust its linkage settings. |
| Dashboard loads slowly on mobile |
The workbook may contain expensive queries or complex visualizations. |
Optimize data, calculations, marks, and dashboard complexity. |
| Wrong layout appears in an embedded view |
The embedded view's dimensions may trigger a different device layout. |
Check the embedded container size and the device-layout selection. |
20. Practical Project: Build a Responsive Sales Dashboard
In this project, you will create a sales dashboard with layouts for desktop, tablet, and phone users.
Project Objective
Create a dashboard that enables managers to review sales performance and regional trends from different devices.
Required Components
- Total Sales KPI.
- Total Profit KPI.
- Order Count KPI.
- Monthly Sales Trend line chart.
- Sales by Region bar chart.
- Sales by Category chart.
- Order Date filter.
- Region filter.
Step 1: Prepare the Worksheets
- Connect Tableau to a sales dataset.
- Create a worksheet for total sales.
- Create a worksheet for total profit.
- Create a worksheet for order count.
- Create a line chart showing sales by month.
- Create a bar chart showing sales by region.
- Create a chart showing sales by product category.
Step 2: Create the Default Dashboard
- Create a new dashboard.
- Choose a suitable initial size.
- Add the KPI worksheets near the top.
- Add the trend and comparison charts.
- Add the required filters.
- Use containers to group related objects.
- Adjust titles, padding, and spacing.
Step 3: Create the Desktop Layout
- Place KPI cards in one row.
- Use side-by-side charts when there is enough space.
- Place filters in a consistent area.
- Check alignment and spacing.
- Verify that chart labels and legends are readable.
Step 4: Create the Tablet Layout
- Open Device Preview and select Tablet.
- Add a tablet layout if one is not already available.
- Arrange KPI cards to fit the tablet width.
- Stack charts if they become too narrow.
- Keep filters accessible and easy to use.
- Test portrait and landscape orientations.
Step 5: Create the Phone Layout
- Open Device Preview and select Phone.
- Add or customize the phone layout.
- Place the most important KPIs first.
- Arrange charts vertically.
- Shorten titles and remove unnecessary objects.
- Keep the most important filters easy to access.
- Choose an appropriate sizing option and test scrolling.
Step 6: Validate the Dashboard
- Review each device layout.
- Check for clipped labels and legends.
- Test all filters and dashboard actions.
- Confirm that the main metrics are easy to find.
- Publish the workbook and test the published version.
21. Example Layout Comparison
| Component |
Desktop |
Tablet |
Phone |
| KPI cards |
One horizontal row |
One or two rows, depending on width |
Stacked or compact arrangement |
| Sales trend |
Wide chart |
Full-width chart where appropriate |
Full-width chart in a vertical sequence |
| Regional chart |
Beside another chart if readable |
Often placed below the trend chart |
Usually stacked below the main KPI section |
| Filters |
Sidebar or top section |
Compact grouped area |
Prioritized controls with careful spacing |
| Navigation |
Multiple sections may be visible together |
Fewer columns |
Simple vertical sequence and scrolling |
22. Interview Questions and Answers
Q1. What is a responsive dashboard in Tableau?
Answer: A responsive dashboard is designed to remain usable across different viewing areas. Tableau supports dashboard sizing options and device-specific layouts to help achieve this.
Q2. What is Device Preview?
Answer: Device Preview is a dashboard authoring feature that lets you inspect the appearance of a dashboard on different device types, models, and orientations.
Q3. What are device-specific layouts?
Answer: Device-specific layouts are customized arrangements of dashboard content for desktop, tablet, and phone viewing.
Q4. What is the difference between Fixed Size and Automatic sizing?
Answer: Fixed Size uses specified dashboard dimensions, while Automatic allows the dashboard dimensions to adapt to the available viewing area. Neither option alone guarantees that all content will remain readable.
Q5. What is Range sizing?
Answer: Range sizing lets the author specify minimum and maximum dashboard dimensions to allow controlled flexibility.
Q6. What is the purpose of a phone layout?
Answer: A phone layout provides an arrangement optimized for a small screen, often using vertically stacked content and fewer visible controls.
Q7. What is the difference between an auto-generated and a custom phone layout?
Answer: An auto-generated phone layout is arranged automatically and may reflect changes to the Default dashboard when linked. A custom phone layout gives the author more control but may require manual maintenance.
Q8. What is Fit All?
Answer: Fit All resizes the dashboard content to fit within the device frame. It should be tested to ensure that text and charts remain readable.
Q9. What is Fit Width?
Answer: Fit Width fits content to the device frame's width while maintaining the layout's fixed height, which can be useful for vertically scrolling phone dashboards.
Q10. Why should mobile dashboards use fewer visualizations?
Answer: Mobile screens have limited space. Focusing on essential visualizations improves readability, reduces clutter, and makes interactions easier.
Q11. Why should device layouts be tested after editing worksheets?
Answer: Changes to worksheets or dashboard content can affect how related device layouts appear. Testing ensures that each layout still works as intended.
Q12. How can you improve dashboard performance on mobile?
Answer: Simplify the dashboard, reduce unnecessary marks and objects, optimize calculations and data sources, and test loading and interaction times.
Q13. Does a phone layout always appear whenever a physical phone is used?
Answer: Not necessarily. Tableau can select a layout based on the dimensions of the viewing area or embedded container, so the layout may depend on the browser or container size.
Q14. Why is portrait and landscape testing important?
Answer: Portrait and landscape orientations have different proportions. Testing both helps identify issues with chart width, scrolling, and the placement of interactive controls.
23. Practical Exercises
Exercise 1: Preview an Existing Dashboard
- Open an existing Tableau dashboard.
- Use Device Preview to inspect desktop, tablet, and phone layouts.
- Record any issues with spacing, labels, charts, or filters.
- Make at least three improvements.
Exercise 2: Create a Phone-Specific Dashboard
- Choose a dashboard with multiple charts.
- Create or customize the phone layout.
- Prioritize the main KPIs.
- Arrange charts vertically.
- Test readability and scrolling.
Exercise 3: Compare Sizing Options
- Test the dashboard with suitable sizing options.
- Compare how the content appears in different device previews.
- Identify when Fit All makes labels too small.
- Evaluate whether Fit Width is suitable for the phone layout.
Exercise 4: Test a Published Dashboard
- Publish your dashboard to the appropriate Tableau environment.
- Open it at different browser window sizes.
- Test the filters, actions, and tooltips.
- Confirm that the intended layout appears.
- Document any remaining problems and correct them.
24. Quick Revision Checklist
- Understand responsive dashboard design.
- Know the difference between Fixed Size, Automatic, and Range sizing.
- Understand Default, Desktop, Tablet, and Phone layouts.
- Know how to open Device Preview.
- Understand how to add a device-specific layout.
- Know the difference between auto-generated and custom phone layouts.
- Understand Fit All and Fit Width.
- Design phone dashboards around the most important metrics.
- Test portrait and landscape orientations.
- Review spacing, labels, filters, and legends at each size.
- Publish and test the actual dashboard in its target environment.
- Check both responsiveness and performance.
25. Official Tableau Learning Resources
26. Tableau Training and Course Demo
Build your Tableau skills by learning dashboard design, visualization, responsive layouts, device previews, and other data analytics techniques through structured training and hands-on practice.
Explore Tableau Training: JustAcademy Tableau Training
Register for a Course Demo: Register for a Tableau Course Demo
27. Conclusion
Responsive dashboard layouts and Device Preview are important Tableau features for creating dashboards that work well across desktop computers, tablets, and mobile phones. Dashboard sizing options provide control over dimensions, while device-specific layouts allow the content to be rearranged for different screen sizes.
For the best results, prioritize the most important metrics, use a clear layout structure, keep text readable, simplify phone interactions, and test every device layout before publishing. Remember that automatic resizing alone does not guarantee a good mobile experience. A well-designed dashboard combines appropriate sizing, thoughtful layout choices, usability, and performance.